home *** CD-ROM | disk | FTP | other *** search
Wrap
EEEELLLLFFFF____FFFFIIIILLLLLLLL((((3333EEEE)))) EEEELLLLFFFF____FFFFIIIILLLLLLLL((((3333EEEE)))) NNNNAAAAMMMMEEEE _eeee_llll_ffff______ffff_iiii_llll_llll - set fill byte SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS _cccc_cccc [_f_l_a_g ...] _f_i_l_e ... _----_llll_eeee_llll_ffff [_l_i_b_r_a_r_y ...] _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_llll_iiii_bbbb_eeee_llll_ffff_...._hhhh_>>>> _vvvv_oooo_iiii_dddd _eeee_llll_ffff______ffff_iiii_llll_llll_((((_iiii_nnnn_tttt _ffff_iiii_llll_llll_))))_;;;; DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN Alignment constraints for ELF files sometimes require the presence of ``holes.'' For example, if the data for one section are required to begin on an eight-byte boundary, but the preceding section is too ``short,'' the library must fill the intervening bytes. These bytes are set to the _f_i_l_l character. The library uses zero bytes unless the application supplies a value. See _eeee_llll_ffff______gggg_eeee_tttt_dddd_aaaa_tttt_aaaa(3E) for more information about these holes. SSSSEEEEEEEE AAAALLLLSSSSOOOO _eeee_llll_ffff(3E), _eeee_llll_ffff______gggg_eeee_tttt_dddd_aaaa_tttt_aaaa(3E), _eeee_llll_ffff______ffff_llll_aaaa_gggg(3E), _eeee_llll_ffff______uuuu_pppp_dddd_aaaa_tttt_eeee(3E). NNNNOOOOTTTTEEEE An application can assume control of the object file organization by setting the _EEEE_LLLL_FFFF______FFFF______LLLL_AAAA_YYYY_OOOO_UUUU_TTTT bit [see _eeee_llll_ffff______ffff_llll_aaaa_gggg(3E)]. When this is done, the library does _n_o_t fill holes. PPPPaaaaggggeeee 1111